Skip creating env variables with undefined values #7047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #7036. From what I can gather, it is possible that env values can be
undefined
.I think we should skip the creation of env if their value is
undefined
.Scenarios Tested
firebase functions:config:set test.user=test-user
firebase functions:config:set some.random.planet=
some.random
doesn't have a valuefirebase functions:config:export
The ff files are created:
.env
.env.default
.env.local